[test] Clear mutex poision if previous host function panicked #819
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ludfjig
changed the title
ludfjig
force-pushed
the
poison_mutex_fix
branch
3 times, most recently
from
09c2499 to
bfe7986
Compare
…eaded Signed-off-by: Ludvig Liljenberg <[email protected]>
ludfjig
force-pushed
the
poison_mutex_fix
branch
from
bfe7986 to
2cd6828
Compare
|
I would like to be careful to avoid adding too much reliance on single-threadedness, since that might change in the future, or at least being extremely clear about where it is and how it would need to change. I also think that a host function failure should probably poison the sandbox, requiring it to be restored before it can be used again? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.